Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 864-tree-1
name: 1499
tree-preservation-order: undefined
864-tpo-1
uprn
address-text
point: POINT (-0.970890 50.866716)
geometry: MULTIPOLYGON (((-0.970776 50.866704,-0.970781 50.866726,-0.970797 50.866746,-0.970822 50.866763,-0.970853 50.866773,-0.970888 50.866777,-0.970924 50.866774,-0.970956 50.866764,-0.970981 50.866748,-0.970998 50.866728,-0.971004 50.866706,-0.970999 50.866684,-0.970983 50.866663,-0.970958 50.866647,-0.970927 50.866637,-0.970892 50.866633,-0.970856 50.866636,-0.970824 50.866646,-0.970799 50.866662,-0.970782 50.866682,-0.970776 50.866704)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL